Systems and Methods for Advanced Energy Network

ABSTRACT

A multiplicity of participants comprising utility operators, distributed energy resource (DER) providers, vendors/aggregators, energy customers, and utility financial officers, are communicatively connected to a platform. The platform provides interactive interfaces for each type of participant to access the platform over communication network. Utility operators are enabled to view and control DER in a certain area via an interface for utility operators. DER providers are enabled to interconnect DER packages to a utility grid via an interface for DER providers. Vendors/aggregators are enabled to view and manage their portfolios via an interface for vendors/aggregators. Energy customers are enabled to view energy information, shop for new products or services, and manage rate plans via an interface for marketplace. Utility financial officers are enabled to view revenue streams from the platform to a utility via an interface for financial settlement.

CROSS-REFERENCES TO RELATED APPLICATIONS

The present invention is related to and claims priority from thefollowing U.S. patent documents: this application is a continuation ofU.S. patent application Ser. No. 15/273,088, filed Sep. 22, 2016, whichclaims priority from U.S. Provisional Patent Application No. 62/222,470,filed Sep. 23, 2015, each of which is incorporated herein by referencein its entirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to electric power messaging andsettlements, and more particularly, to advanced energy settlements,messaging, and applications for electric power supply, load, and/orcurtailment and data analytics associated with the same.

2. Description of the Prior Art

Generally, it is known in the prior art to provide electric powersystems management, including financial settlements and messaging.However, limited information is available to electric power consumersregarding their past, present, and future projected use of power withsufficient details to make informed choices about types of power supplyand pricing alternatives. Furthermore, retail electric providers (REPs)in prior art systems and methods do not have access to data andanalytics to provide optimal pricing for power supplied to businessand/or residential electricity customers, and do not have the ability toprovide advanced energy settlements to provide the lowest pricing forpower supplied at predetermined times, due at least in part to costsassociated with obtaining power agreements without visibility to thedata and analytics that provide a reduced risk of capital andperformance associated with the supply and demand sides. Thus, thereremains a need for improved information, controls, real-time ornear-real-time data on power consumption and production for electricpower market participants, REPs, customers, data centers, and microgridowners, and messaging and management of financial settlement therefor.

SUMMARY OF THE INVENTION

The present invention relates to electric power messaging andsettlements, and more particularly, to advanced energy settlements,messaging, and applications for electric power supply, load, and/orcurtailment and data analytics associated with the same. Systems andmethods for data analytics and customer or consumer guidance andcontrols are provided, and coupled with graphical user interfaces forinteractive control and command of grid elements, design, specification,construction, management and financial settlement for data centersand/or microgrids, business and residential power consumption, control,management, messaging and settlements, mobile applications, websites,marketing offers, optimal pricing for comparable energy plans, retailelectric provider and direct consumer alternatives, network of powerarchitecture, EnergyNet applications, software development kits,application web-based storefronts, and combinations thereof.

The present invention provides for systems, methods, and graphical userinterface (GUI) embodiments for providing electric power usage (past,current, and/or future projected) information, management, financialsettlements, and messaging, and applications as described herein.

These and other aspects of the present invention will become apparent tothose skilled in the art after a reading of the following description ofthe preferred embodiment when considered with the drawings, as theysupport the claimed invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a network of microgrids integratedwith an EnergyNet platform.

FIG. 2 illustrates another embodiment of a network of microgridsintegrated with an EnergyNet platform.

FIG. 3 is a schematic diagram of Federated Microgrid Communitiescomprising different grid zones.

FIG. 4 is a schematic diagram of an embodiment showing a configurationfor a cloud-based computing system allowing users to interface with thesystems of the present invention.

FIG. 5 illustrates method steps for providing advanced energysettlements (AES) according to one embodiment of the present invention.

FIG. 6 is a schematic diagram illustrating a high-level AES systemarchitecture according to the present invention.

FIG. 7 is a schematic diagram illustrating an exemplary EnergyNetgateway according to the present invention.

FIG. 8 is a schematic diagram illustrating a partial list of exemplarygrid elements according to the present invention.

FIG. 9 is a schematic diagram illustrating components of the systems andmethods of the present invention.

FIG. 10 continues to illustrate components of the systems and methods ofthe present invention shown in FIG. 9.

FIG. 11 is a schematic diagram illustrating a grid application model ofthe systems and methods of the present invention.

FIG. 12 is a schematic diagram illustrating a high-level systemarchitecture for an EnergyNet embodiment according to the presentinvention.

FIG. 13 is a schematic and flow diagram illustrating AES sequencing.

FIG. 14 is a schematic diagram illustrating AES evolution for thesystems and methods of the present invention.

FIG. 15 is a block diagram for the functions of a utility operatorinterface provided by an EnergyNet data platform.

FIG. 16 is a screenshot of a utility operator interface showing a heatmap of a distributed energy resource (DER) in a certain area displayingproduction capacity distribution by circuit view.

FIG. 17 is a screenshot of a utility operator interface showing energyproduction in a certain area by region.

FIG. 18 is a screenshot of a utility operator interface showing a heatmap of a DER displaying production capacity distribution by segmentview.

FIG. 19 is a screenshot of a utility operator interface showing atabular and graphic description of different segments.

FIG. 20 is a screenshot of a utility operator interface providing a mapof different DERs sites in a certain segment and information regardingeach site's configuration.

FIG. 21 is a screenshot of a utility operator interface showing adetailed energy description of a specific site.

FIG. 22 is a screenshot of a utility operator interface describing thegrid configuration of a specific site and showing the energy demand andusage of a specific site.

FIG. 23 is a block diagram for the functions of an interconnectionprocessing interface provided by an EnergyNet data platform.

FIG. 24 is a screenshot of an interconnection processing interfaceshowing interconnection progress by site.

FIG. 25 is a screenshot of an interconnection processing interfacedisplaying pre-approved production packages and listing interconnects inprogress.

FIG. 26 is a screenshot of an interconnection processing interfacedisplaying the scope and technical description for an interconnectionapplication submitted for review.

FIG. 27 is a screenshot of an interconnection processing interfacedisplaying information about the interconnection agreement for aninterconnection application assigned to an engineer for review.

FIG. 28 is a block diagram for the functions of a vendor/aggregator viewinterface provided by an EnergyNet data platform.

FIG. 29 is a screenshot of a vendor/aggregator view interface listingtop customer segments, top sellers in the marketplace, top campaigns inthe marketplace, and pre-approved production zones.

FIG. 30 is a screenshot of a vendor/aggregator view interface displayingcustomer segment research for vendors/aggregators.

FIG. 31 is a screenshot of a vendor/aggregator view interface displayingsubmission of a device for catalog content review.

FIG. 32 is a block diagram for the functions of a marketplace viewinterface provided by an EnergyNet data platform.

FIG. 33 is a screenshot of the log in screen for a marketplace viewinterface.

FIG. 34 is a screenshot of a marketplace view interface displaying acustomer's buildings on a map and information related to energy usage atthe buildings.

FIG. 35 continues to illustrate the marketplace view interface of FIG.34 with an overlay providing information about a specific building.

FIG. 36 is a screenshot of a marketplace view interface displaying thedescription, energy rate, current/average usage, and daily cost for asite.

FIG. 37 is a screenshot of a marketplace view interface displayingcurrent energy usage.

FIG. 38 is a screenshot of a marketplace view interface displaying pastenergy usage.

FIG. 39 is a screenshot of a marketplace view interface allowing usersto compare the energy use of different buildings.

FIG. 40 continues to illustrate the marketplace view interface of FIG.39 with an overlay showing a brief description of a selected building.

FIG. 41 is a screenshot of a marketplace view interface showing acomparison between two buildings.

FIG. 42 continues to illustrate the marketplace view interface of FIG.41 with an overlay showing a recommendation to install an electricvehicle charging station.

FIG. 43 is a screenshot of a marketplace view interface showing thecurrent status of a customer's grid.

FIG. 44 is a screenshot of the home page of the marketplace forcommercial and industrial customers, residential customers, and popularapps.

FIG. 45 is a screenshot showing upgrade options in a marketplace viewinterface.

FIG. 46 is another screenshot showing upgrade options in a marketplaceview interface.

FIG. 47 is a screenshot showing a rate plan selector in a marketplaceview interface.

FIG. 48 continues to illustrate the marketplace view interface of FIG.47 with an overlay showing a description of a selected plan.

FIG. 49 is a screenshot of a marketplace view interface displaying otherservices provided by the marketplace.

FIG. 50 is a screenshot of a marketplace view interface showing thepayments dashboard.

FIG. 51 is a block diagram for the functions of a financial settlementview interface provided by an EnergyNet data platform.

FIG. 52 is a screenshot of a financial settlement view interface showingthe settlements dashboard.

FIG. 53 is a screenshot of a financial settlement view interface showingrecent transactions.

FIG. 54A and FIG. 54B are screenshots of a utility bill verification foran electric bill. FIG. 54A is the left side of the screen and FIG. 54Bis the right side of the screen.

FIG. 55A and FIG. 55B are screenshots of a utility bill verification foran electric and gas bill. FIG. 55A is the left side of the screen andFIG. 55B is the right side of the screen.

FIG. 56 is a screenshot of a map of an electrical spend map zoomed outto show the Continental United States.

FIG. 57 is a screenshot of a map of an electrical spend map zoomed in tothe region level.

FIG. 58 is a screenshot of a map of an electrical spend map zoomed in tothe district level.

FIG. 59 is a screenshot of a map of an electrical spend map zoomed in tothe neighborhood level.

FIG. 60 is a screenshot of a sample settlement pricing zone.

FIG. 61 continues to illustrate the screenshot of FIG. 60 withadditional map layers for ERCOT Settlement Points.

FIG. 62 is a screenshot showing a satellite image of actual settlementpoints.

FIG. 63 is a screenshot of an overview of ERCOT Settlement Zones.

FIG. 64 is a screenshot of the log in screen for a financial modelvisualization interface.

FIG. 65 is a screenshot showing the selection of the financial modelfrom the dropdown menu.

FIG. 66 is a screenshot of a financial model page.

FIG. 67 is a screenshot showing kilowatt hour (kWh) Usage Distributionand kWh Generation Distribution.

FIG. 68 is a screenshot of a simulation showing meter distributionsrandomly added to the map over time.

FIG. 69 continues to illustrate the screenshot of FIG. 68 withadditional map layers for ERCOT Settlement Points.

DETAILED DESCRIPTION

Referring now to the drawings in general, the illustrations are for thepurpose of describing preferred embodiment(s) of the invention at thistime, and are not intended to limit the invention thereto. Any and alltext associated with the figures as illustrated is hereby incorporatedby reference in this detailed description.

The present invention provides systems and methods for data analysis,messaging, advanced energy settlements, command and control andmanagement of electric power supply, demand, and/or curtailmentincluding graphical user interfaces for consumers, including consumerprofiles and alternative pricing programs and/or settlement programs forbusiness and residential applications, including but not limited tographical user interfaces for interactive control and command of gridelements, design, specification, construction, management and financialsettlement for data centers and/or microgrids, business and residentialpower consumption, control, management, messaging and settlements,mobile applications, websites, marketing offers, optimal pricing forcomparable energy plans, retail electric provider and direct consumeralternatives, network of power architecture, EnergyNet applications,software development kits, application web-based storefronts, andcombinations thereof. Apparatus embodiments are also provided inaccordance with the systems and methods described herein.

Furthermore, novel methods of the present invention provide for consumerguidance and controls that are coupled with graphical user interfacesfor mobile applications, websites, and computer displays that provideimproved information and controls for consumers for electric powerconsumption and management of financial settlement therefor. Preferably,the customer sets their preferences through the user interfaces and thenthe customer's own data, including whether the customer has opted in fordirect response participation, is used to make recommendations for gridelements, services, etc., to the end users, and inputs or opt in/outrelating to permissions of data use (e.g., meter data aggregator usage).

In the description of the present invention, it will be understood thatall EnergyNet embodiments and AES systems and methods descriptionsinclude and incorporate by this reference without regard to individual,specific recitation for each example described, real-time and/ornear-real-time data, including revenue grade metrology used for AESfinancial settlements. Revenue grade metrology data, which a genericcomputer is incapable of using, is generated by active grid elements inthe power grid; measured data is then transformed into settlement gradedata for market financial settlement for load and supply. Additionallyand similarly, real-time communication, messaging, and data packettransfer is provided over at least one network associated with thesystems and methods of the present invention. This requires physicaldevices, including at least one client device and at least one server,communicating and interacting over the network. The present invention isnecessarily rooted in computer technology in order to overcome a problemspecifically arising in the realm of computer networks, morespecifically, advanced energy settlements, messaging, and applicationsfor electric power supply, load, and/or curtailment and data analyticsassociated with the same.

This detailed description of the present invention includes energyfinancial settlements and messaging and/or data packet transfer ortransmission, including the following issued patents and/or copendingapplications by common inventor and/or assignee Causam Energy, Inc.:U.S. Pat. Nos. 8,849,715, 8,583,520, 8,595,094, 8,719,125, 8,706,583,8,706,584, 8,775,283, 8,768,799, 8,588,991, and 8,761,952, each of whichis incorporated by reference in its entirety herein; US PatentPublication Nos. 2014/0180884, 2014/0279326, 2014/0277788, 2014/0039701,2014/0277786, and 2014/0277787, each of which is incorporated byreference in its entirety herein; and WIPO Publication Nos.WO2014/066087, 2014/0039699, and WO2014/022596, each of which isincorporated by reference in its entirety herein.

The systems and methods of the present invention also provide supportand functionality for at least one distribution service provider throughthe market-based platform to allow communities, municipalities,cooperative power groups, and/or other combinations of persons orentities to be aggregated to form at least one distribution serviceprovider, which may exist within another distribution service provider,transmission/distribution service provider (TDSP), and/or utility.Additionally, a meter data aggregator (MDA) is provided to interfacewith the distribution service provider and power marketer and/orutility.

FIG. 1 illustrates an embodiment of a network of microgrids integratedwith an EnergyNet platform. There are two microgrids, Microgrid A andMicrogrid B, electrically and communicatively integrated to a network ofpower. An EnergyNet platform is coupled to the network of power. Thenetwork of power gathers metrology, settlement, and contract managementdata from Microgrid A and Microgrid B. The EnergyNet platform has itsapplication stack including security, provisioning, auditing,visualization, analytics, rules, workflow, and event management. TheEnergyNet platform provides consumer engagement.

FIG. 2 illustrates another embodiment of a network of microgridsintegrated with an EnergyNet platform. There are two microgrids,Microgrid A and Microgrid B. Microgrid B is electrically andcommunicatively integrated to a network of power, and provides gridcontrol, demand response, real-time modeling, and data acquisition.Microgrid A is externally linked to a real-time modeling module. BothMicrogrid A and the real-time modeling module are connected to thenetwork of power for providing grid control, demand response, real-timemodeling, and data acquisition. The network of power provides gridelement profiles, models and/or topologies, energy settlement, financialsettlement, reporting, and third party integration. The network of poweris coupled with an EnergyNet platform, which provides consumerengagement on at least one level and preferably on a multiplicity oflevels providing for varying levels or degrees of user engagement (e.g.,level 0 to level 4, described hereinbelow) from consumer energyconsumption from historical data (at least one electrical power bill)uploaded to the platform or system, to grid element introduction andload curtailment or power supply through managed or command and controlprograms operated by or on behalf of at least one utility or marketparticipant, to vendor interaction and retail electric provider or dataaggregator engagement via digital contracts accepted within the electricmarkets for market-based financial settlement and energy settlement.

FIG. 3 is a schematic diagram of Federated Microgrid Communities. Thesemicrogrid communities are located in different grid zones. Each of themicrogrid communities has a structure as shown in FIG. 2. There arecommunication links between different microgrid communities within agrid zone.

The present invention includes a multiplicity of interactive graphicaluser interfaces (GUIs) for all aspects of AES and/or EnergyNetembodiments. By way of example and not limitation, as illustrated in thefigures, at least one GUI is provided for electric power consumption forbusiness or commercial facilities, including information and/or controlswherein the GUI is provided for mobile applications, websites, terminaland/or computer displays, and combinations thereof. For mobileapplications, one embodiment includes a mobile communication computerdevice, such as a smartphone, tablet computer, or other mobile smartinteractive communications device (personal/wearable or portable),having an application including software operable on a processor coupledwith memory, wherein the mobile communication computer device isconstructed and configured for network-based communication within acloud-based computing system as illustrated in FIG. 4.

FIG. 4 is a schematic diagram of an embodiment of the inventionillustrating a computer system, generally described as 800, having anetwork 810 and a plurality of computing devices 820, 830, 840. In oneembodiment of the invention, the system 800 includes a cloud-basednetwork 810 for distributed communication via a wireless communicationantenna 812 and processing by at least one mobile communicationcomputing device 830. In another embodiment of the invention, the system800 is a virtualized computing system capable of executing any or allaspects of software and/or application components presented herein onthe computing devices 820, 830, 840. In certain aspects, the computersystem 800 may be implemented using hardware or a combination ofsoftware and hardware, either in a dedicated computing device, orintegrated into another entity, or distributed across multiple entitiesor computing devices.

By way of example, and not limitation, the computing devices 820, 830,840 are intended to represent various forms of digital computers andmobile devices, such as a server, blade server, mainframe, mobile phone,personal digital assistant (PDA), smartphone, desktop computer, netbookcomputer, tablet computer, workstation, laptop, and other similarcomputing devices. The components shown here, their connections andrelationships, and their functions are meant to be exemplary only, andare not meant to limit implementations of the invention described and/orclaimed in this document

In one embodiment, the computing device 820 includes components such asa processor 860, a system memory 862 having a random access memory (RAM)864 and a read-only memory (ROM) 866, and a system bus 868 that couplesthe memory 862 to the processor 860. In another embodiment, thecomputing device 830 may additionally include components such as astorage device 890 for storing the operating system 892 and one or moreapplication programs 894, a network interface unit 896, and/or aninput/output controller 898. Each of the components may be coupled toeach other through at least one bus 868. The input/output controller 898may receive and process input from, or provide output to, a number ofother devices 899, including, but not limited to, alphanumeric inputdevices, mice, electronic styluses, display units, touch screens, signalgeneration devices (e.g., speakers), or printers.

By way of example, and not limitation, the processor 860 may be ageneral-purpose microprocessor (e.g., a central processing unit (CPU)),a graphics processing unit (GPU), a microcontroller, a Digital SignalProcessor (DSP), an Application Specific Integrated Circuit (ASIC), aField Programmable Gate Array (FPGA), a Programmable Logic Device (PLD),a controller, a state machine, gated or transistor logic, discretehardware components, or any other suitable entity or combinationsthereof that can perform calculations, process instructions forexecution, and/or other manipulations of information.

In another implementation, shown as 840 in FIG. 4, multiple processors860 and/or multiple buses 868 may be used, as appropriate, along withmultiple memories 862 of multiple types (e.g., a combination of a DSPand a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core).

Also, multiple computing devices may be connected, with each deviceproviding portions of the necessary operations (e.g., a server bank, agroup of blade servers, or a multi-processor system). Alternatively,some steps or methods may be performed by circuitry that is specific toa given function.

According to various embodiments, the computer system 800 may operate ina networked environment using logical connections to local and/or remotecomputing devices 820, 830, 840 through a network 810. A computingdevice 830 may connect to a network 810 through a network interface unit896 connected to a bus 868. Computing devices may communicatecommunication media through wired networks, direct-wired connections, orwirelessly, such as acoustic, RF, or infrared, through an antenna 897 incommunication with the network antenna 812 and the network interfaceunit 896, which may include digital signal processing circuitry whennecessary. The network interface unit 896 may provide for communicationsunder various modes or protocols.

In one or more exemplary aspects, the instructions may be implemented inhardware, software, firmware, or any combinations thereof. A computerreadable medium may provide volatile or non-volatile storage for one ormore sets of instructions, such as operating systems, data structures,program modules, applications, or other data embodying any one or moreof the methodologies or functions described herein. The computerreadable medium may include the memory 862, the processor 860, and/orthe storage media 890 and may be a single medium or multiple media(e.g., a centralized or distributed computer system) that store the oneor more sets of instructions 900. Non-transitory computer readable mediaincludes all computer readable media, with the sole exception being atransitory, propagating signal per se. The instructions 900 may furtherbe transmitted or received over the network 810 via the networkinterface unit 896 as communication media, which may include a modulateddata signal, such as a carrier wave or other transport mechanism, andincludes any delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics changed or set in amanner as to encode information in the signal.

Storage devices 890 and memory 862 include, but are not limited to,volatile and non-volatile media such as cache, RAM, ROM, EPROM, EEPROM,FLASH memory, or other solid state memory technology; discs (e.g.,digital versatile discs (DVD), HD-DVD, BLU-RAY, compact disc (CD), orCD-ROM) or other optical storage; magnetic cassettes, magnetic tape,magnetic disk storage, floppy disk, or other magnetic storage devices;or any other medium that can be used to store the computer readableinstructions and which can be accessed by the computer system 800.

It is also contemplated that the computer system 800 may not include allof the components shown in FIG. 4, may include other components that arenot explicitly shown in FIG. 4, or may utilize an architecturecompletely different than that shown in FIG. 4. The various illustrativelogical blocks, modules, elements, circuits, and algorithms described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, computer software, or combinations of both. Toclearly illustrate this interchangeability of hardware and software,various illustrative components, blocks, modules, circuits, and stepshave been described above generally in terms of their functionality.Whether such functionality is implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system. Skilled artisans may implement the describedfunctionality in varying ways for each particular application (e.g.,arranged in a different order or partitioned in a different way), butsuch implementation decisions should not be interpreted as causing adeparture from the scope of the present invention.

In one embodiment, the application (e.g., smartphone app) automaticallyprovides information via the GUI associated with the app to indicate tothe user (consumer) information about electric pricing planalternatives, including but not limited to their location, the price forelectric power supply on any per unit (e.g., data center, microgrid,building type (commercial or residential), facility, device, gridelement, and combinations thereof) basis for a duration and/or at apredetermined time, and combinations thereof. Also, preferably the appGUI provides additional information including marketing and advertisinginformation about any merchants, products, and/or services associatedwith or related to their profile(s), power usage, activities within thesystem, and combinations thereof. Also preferably, the app GUI providesan interactive interface allowing inputs to be received for generatingat least one account and corresponding profile, advanced energysettlements selections, etc. In one embodiment of the present invention,the received inputs are associated with a consumer or user profile thatis stored on the smartphone and/or in a database associated with aserver computer and/or cloud-based computing system with at least oneserver computer and at least one database having remote inputs andoutputs via the data and communications network, preferably via secureaccess and/or secure messaging for authorized users associated with theat least one account.

In a virtualized or cloud-based computing system and methods of thepresent invention, the following components are provided as illustratedby way of example and not limitation to those described in FIG. 4.Components of a cloud-based computing system and network for distributedcommunication therewith by mobile communication devices include but arenot limited to a server computer with a processing unit. The server isconstructed, configured, and coupled to enable communication over anetwork. The server provides for user interconnection with the serverover the network using a remote computer device or a personal computer(PC), smartphone, tablet computer, etc., positioned remotely from theserver. Furthermore, the system is operable for a multiplicity of remotepersonal computers or terminals, for example, in a client/serverarchitecture, as shown. Alternatively, a user may interconnect throughthe network using a user device such as a personal digital assistant(PDA), mobile communication device, such as by way of example and notlimitation, a mobile phone, cell phone, smartphone, tablet computer,laptop computer, netbook, terminal, in car computer, or any othercomputing device suitable for network connection. Also, alternativearchitectures may be used instead of the client/server architecture. Forexample, a computer communications network, or other suitablearchitecture may be used. The network may be the Internet, an intranet,or any other network suitable for searching, obtaining, and/or usinginformation and/or communications. The system of the present inventionfurther includes an operating system installed and running on theserver, enabling the server to communicate through the network with theremote, distributed user devices. The operating system may be anyoperating system known in the art that is suitable for networkcommunication.

FIG. 5 illustrates method steps for providing advanced energysettlements (AES) according to one embodiment of the present invention.A settlement AES process is outlined in six distinct steps as follows:(1) revenue grade settlement block data is used to underpin thesettlement process for the billing period (e.g., daily, weekly, monthly,predict & pay); (2) settlement block data is mapped to the appropriatedistributed or fixed energy power purchase agreement in effect at thatpoint in time; (3) the cost of each settlement block inclusive of Timeof Use (TOU), demand, taxes, access fees, and energy charges iscalculated; (4) a customer balance is calculated from all the settlementblocks that apply within the period and automatically collected from thecustomer; (5) distributed energy charges for all customers billed in thecycle are aggregated by generator and settled through the clearinghouse; and (6) fixed energy charges for all customers billed in thecycle are aggregated and settled with the energy retailer or REP.

The EnergyNet data platform used with AES preferably provides and/or isoperable for real-time revenue grade data ingress; stores and organizespacket level information that can be used for forecasting, data mining,revenue extraction, event detection, sophisticated energy management,and enterprise integration purposes; aggregates and stores revenue datainto revenue grade settlement blocks (or Power Trading Blocks (PTBs));connects microgrid and spot market buyers and sellers; provides a fullyautomated and low latency industry leading settlement processunderpinned by a distributed settlement rules engine capable of settlingwith both distributed and fixed generator market participants; providesan automated payment exchange which supports all advanced billing models(e.g., shared data plan, daily plan, predict & pay); manages payments assingle energy bills for customers with EnergyNet responsible forsettlement payments between multiple distributed energy generators andthe customer's existing energy retailer; provides a real-time energypurchasing solution that matches the customer's real energy consumptionagainst energy currently available within the microgrid or spot market;captures and transforms market data that can provide intelligentanalytics by generators for trending, forecasting, planning, andmaximizing revenue/investment opportunities; captures and transformsenergy data that can provide intelligent analytics for customers' energymanagement, forecasting, procurement, profiling, bill optimization, andrecommendation purposes; and integrates with the existing distributedenergy market exchange to allow EnergyNet buyers and sellers to connectand agree prices on distributed generation. As illustrated in FIG. 11,EnergyNet grid applications ensure that the EnergyNet framework isoperable to support 1:n grid applications. Third party infrastructuremay provide Service-Oriented Architecture (SOA) integration with utilityand/or market participant enterprise systems; provide SOA integrationwith general ledger and accounting systems; and/or provide SOAintegration with the financial, banking, and clearing infrastructure, asneeded.

For example, in a microgrid management application the EnergyNetplatform is transacting between the market, utility, consumers, REPs,distribution service providers, balancing authorities, etc. The energymanagement system (EMS) power model includes data for frequency,voltage, VARs, state estimation, SCED, and actual or real-timeinformation. Data associated with the microgrid is communicated over asecure IP network. The GUIs of the present invention allow formonitoring the market conditions or grid stability conditions assignaled by the distribution service providers, utilities, etc.; it alsoallows for monitoring of normal conditions, reserves, forecastconditions, etc. External triggers for the EMS may include changes inforecast conditions, actual conditions, market conditions, market price,schedule based upon forecast price exceeding operating cost for themicrogrid, etc. Software as a Service (SaaS) operable within the systemsand methods of the present invention provides for dispatch of load andsupply via EMS systems for distributed assets, wherein the microgrid isconsidered its own balancing area. So the various external triggers,including the market and/or market-based pricing, are operable as inputsto activate the isolation or connection of the microgrid according tothe profile associated with the microgrid. In one embodiment, themicrogrid is a secure, critical infrastructure (such as, by way ofexample and not limited to, data centers) and/or a military installationor facility, wherein the microgrid is locally managed in GUIs andsoftware for grid stability and function such that the computer andsoftware that controls the microgrid and its grid elements are locatedwithin the geographic footprint of the microgrid to enable it tofunction as its own balancing authority shielded from any externalcontrols of the electrical power flows within it. A microgrid isconsidered any sub-grid, power generating asset, or power supplyingasset that can island itself from the electric power grid and/or connector reconnect with the main electric power grid (having external controlsfrom the microgrid).

FIG. 6 is a schematic diagram illustrating a high-level AES systemarchitecture according to the present invention. The principal actorsand data flows are depicted in FIGS. 6, 12, and 13 for EnergyNetembodiments. Customers receive near-real-time market connection data andprice signals through the EnergyNet platform, giving visibility togenerated power as it becomes available in the market. This data is usedby EnergyNet to facilitate intelligent energy purchasing and settlementbetween all market participants. Distributed Generators advertiseavailable energy to EnergyNet customers with power purchase offeringspublished within the EnergyNet platform, ensuring that intelligentenergy purchasing decisions can be automated or recommended by EnergyNetwithin a real-time market. Customers with the capacity to both generateand export energy (i.e., if they have an exportable capacity) can alsoact as generators through EnergyNet. Customer Payments received from aCustomer Bank represent consolidated single payments to EnergyNet forenergy purchased on both the fixed and distributed generation market(i.e., supplied by their existing Energy Retailer or DistributedGenerators). Settlements are apportioned across revenue grade TOU meterreadings over a billing period; internal usage is measured throughreal-time sub-metering technology at 1 second intervals and/or near realtime or real time. EnergyNet supports the billing of sub-meteredentities, allowing the EnergyNet customer to resell or cross chargeenergy using the sub-metered meter readings. The EnergyNet customerinstance allows these energy costs to be recovered against theenterprise's total energy consumption. Distributed Generators/generationsupplier participants receive cleared settlements from a DistributedGenerator Bank for all energy consumed within the billing timelinesspecified in the distributed power purchase agreements of EnergyNetcustomers. The Distributed Generator Bank receives aggregated andcleared settlements from a Clearing House for distributed energy thatwas consumed under each distributed power purchase agreement held byEnergyNet customers. The Clearing House receives all uncleareddistributed energy settlements made through EnergyNet's point of saledevices or advanced billing methods before passing the clearedsettlements to the Distributed Generator Bank. EnergyNet performs allsettlement activities for all participants in a transaction. EnergyNetcan also manage the payments for energy resold or cross charged by thecustomer. This can be viewed and analyzed against the imported energybill. Customers can still consume energy supplied by fixed generators(e.g., Energy Retailers, REPs) outside the spot energy or micro market;the portion of a customer's consumption that resides within their fixedgeneration power purchase agreement will be settled with the retailer.The settlement algorithms resolve this using settlement blocks, allpower purchase agreements in place, and data generated by revenue grademeter. Purchasing within the spot market requires prices to benegotiated and agreed to in seconds, and these activities requireintegration with existing market trading systems. A growing customerbase allows EnergyNet to provide a complete trading market betweenusers. The purchasing rules engine criteria allows generators to respondto customer preferences and offer a variety of different tariffs as wellas alter their own behavior (e.g., if they are a customer/generator canthey shift their highest usage off peak and export excess energy at peakperiods when demand and prices are higher).

FIG. 7 is a schematic diagram illustrating an exemplary EnergyNetgateway according to the present invention. The EnergyNet gateway in thepresent invention connects different participants having differentnetwork protocols to the advanced energy settlement platform. Thedifferent participants include green communities, microgrid operators,building managers, market participants, and retail utilities. TheEnergyNet gateway is also used for peering interconnections. Differentcommunication protocols/standards may be supported by the EnergyNetgateway (e.g., LTE, 3G, 1 GBps, VPN, IPSec, ModBus, DNP3, kWp, KYZ,JDBC, REST, WiFi, Zigbee, SEP, PLC, BLE). At the local level, theEnergyNet gateway is operable for monitoring, control, detection,management, reliability, and analysis. At network level, the EnergyNetgateway is operable for profiling, response, settlement, applications,and recommendations. Zigbee Hadoop or any distributed DB or structurecapable of receiving large amounts of data, whether structured orunstructured data.

FIG. 8 is a schematic diagram illustrating a partial list of exemplarygrid elements according to the present invention. The grid elementsinclude but are not limited to power transfer switches, wind meters,utility meters, battery discharge controllers, tenant sub-meters, solarmeters, power distribution units (PDUs), appliance switches, electricvehicle charging stations, distributed energy resources (DERs), transferswitches, electric vehicle batteries, inverters, controllable loads,weather stations, and HVAC environments.

FIGS. 9 and 10 are schematic diagrams illustrating components of thesystems and methods of the present invention. The systems of the presentinvention include on premise physical instances, an IP network, a Causamdata center, an EnergyNet Content Storefront, at least one EnergyNetDistribution Partner, an EnergyNet Market Interface, and UtilityInfrastructure at the Energy Supplier. The on premise physicalinstances, such as Ethernet meters, WiFi/Bluetooth thermostats, utilitymeters, solar inverter battery arrays, KYZ Pulse meters, and devicesusing MODBUS, DNP3, or Foreseer, are connected to an IP network throughan EnergyNet gateway, a carrier network card, a VirtuWatt Red Lion, or aPaladin gateway. The Causam data center has a physical layer thatincludes EnergyNet Ingress for meter data management (MDM);provisioning, security and licensing; and EnergyNet Hadoop for analysis.The Causam data center further includes a cloud application layerproviding event detection, third party App instances, mobile and webuser interfaces, purchasing and settlements, monitoring,Service-Oriented Architecture (SOA) and Software Development Kit (SDK)services, profiling and trending analytics, modeling and forecasting,demand response, distributed generation management, virtual power plant(VPP), and outage management. The EnergyNet Content Storefront providesthird party App reference, which has one-way communication to the thirdparty App instance in the Causam data center for cloud Virtual Machine(VM), App replication, App review, and provision process. The EnergyNetContent Storefront also provides shopping and marketing directed toconsumers and generators. The EnergyNet Distribution Partner includesinstallers, HVAC technicians, and financing institutions, who serve as areferral network, fulfill orders, and provide services. The EnergyNetMarket Interface connects with regulation agencies, for example ERCOTand other RTOs, for signaling and pricing. The Energy Supplier can be aninvestor-owned utility (IOU), REP, and/or municipal power agency. TheUtility Infrastructure at the Energy Supplier provides applications,such as VPP, Distribution Management System (DMS), and DER applications,and Utility Enterprise Infrastructure. The Utility EnterpriseInfrastructure communicates with the SOA and SDK services at the Causamdata center via IPSec and/or VPN for standard or customer SOAintegration. AMI system feeds directly into EnergyNet or into a meterdata management system that then communicates the data to the EnergyNetplatform.

FIG. 11 is a schematic diagram illustrating a grid application model ofthe systems and methods of the present invention. The EnergyNet GridApplication Model includes aggregated market view, existing utilityadvanced metering infrastructure (AMI), EnergyNet Data Platform,EnergyNet Grid Applications, and third party infrastructure. Theaggregated market view provides information such as market level trends,traffic, line losses, and risk. The existing utility AMI includesmulti-AMI for head end systems, grid elements for sensing, grid elementsfor controlling, multi-devices/vendors, and multi-network. The EnergyNetData Platform provides application program interfaces (APIs) for dataingress, event detection, profiling and forecasting, analytics andintelligence, payments and settlements, and recommendations. Themulti-AMI for head end systems in the existing utility AMI providesmarketing confirmation to data ingress on the EnergyNet Data Platform.The recommendations provided by the EnergyNet Data Platform aremarketing recommendations provided to multi-network in the existingUtility AMI. EnergyNet Grid Applications include multiple gridapplications. For example, grid application 1 is for data presentment,pre-payment, data collaborations, and shopping carts for commercialconsumers; grid application 2 is for customer recruiting, behaviorrecommendations, and bill optimization for retail electric providers;grid application 3 is for point of sale, charging stations, merchant andmarketing integration for an electric vehicle network; grid application4 is for financial routing instructions and point of sale terminals forREP to generator settlements; etc. Third party infrastructure includesSOA for utility enterprise; consumer information; general ledger andaccounting; billing, payment, and banks; marketing and strategy; andcapitalization and investment.

FIG. 12 is a schematic diagram illustrating a high-level systemarchitecture for an EnergyNet embodiment according to the presentinvention. This high-level system architecture includes a customerdeployable distributed EnergyNet Customer Instance providing customerswith a complete energy management, purchasing, and settlement solutionwithin the microgrid and spot generation market for AES.

FIG. 13 is a schematic and flow diagram illustrating AES sequencing.There are four key elements within the EnergyNet enterprise financialsettlement product: data ingress, market participation, paymentscollection, and advanced energy settlements. Intelligent purchasingdecisions require advanced smart metering, and EnergyNet uses high speedIP metering technology to build a complete and real-time energyconsumption profile aggregated from multiple sub-metering points. Allconsumption data within the enterprise forms settlement blocks, whichare used to drive the billing and settlement process. All metering datais aggregated to provide a real-time settlement block and totalenterprise consumption view with drill down. This data forms the basisfor billing, settlement, forecasting, market view, and other analyticaltransformations. Note that EnergyNet can also utilize less dynamic datafrom legacy meters and head end systems where a customer investment inconventional sub-metering has already been made. Profiling is animportant element for customers to forecast future usage and committingto purchase offerings. Time of Use (TOU) and/or demand profiles createdfrom base data are an important tool for customers and generators alike;industry standard profiling techniques can be used to create profiles.Generators can use profiles to price their products and plan theirgeneration activities. Customers can use profiles to ensure they committo the power purchase offerings that are best aligned with theiranticipated usage.

Buyers and sellers of electric power are connected within the microgridor spot market associated with AES of the present invention. Sellers canadvertise their generated capacity to customers in near real time andcustomers can make intelligent purchasing decisions based uponactionable real-time data. The Advanced Energy Settlement (AES) processperforms all billing, payment, and settlement activities with financialand clearing participants. A configurable market purchasing rules engineranks and selects energy from the market based on customer preferencessuch as cost, payment preference, locality, renewability of the energy,market supply, consumption, etc., and may recommend purchasing from oneor more suppliers. The suitability of the offering also depends onadditional factors, such as any minimum and maximum usage constraints,which requires decisions to be made based upon forecasts derived usinghistorical data and profiles stored within EnergyNet.

FIG. 14 is a schematic diagram illustrating AES evolution for thesystems and methods of the present invention. The advanced energysettlements in the present invention has an EnergyNet Platform incommunication with a clearing house, which does the settlements betweenthe generator bank and the consumer bank. This requires fewerparticipants than legacy settlements, which results in simplifiedcommunications between the participants.

The EnergyNet data platform provides distinct graphic user interfaces(GUIs) for various participants of advanced energy settlements. In oneembodiment, the GUIs are web-based interfaces. In another embodiment,the GUIs are interfaces of mobile application programs (Apps) forvarious participants.

The GUI enables simulation and modeling for building demand responseresources DERs, microgrids, etc., allowing for a drag and drop thatautomatically triggers generation of a power model and a pro forma modelhaving at least one generator and/or at least one load device associatedwith it, and an engineering interconnection based upon location,equipment, grid identifier, geodetic information, attachment pointinformation, etc. The model considers collected data provided by thecustomer, historical data, and the current environment of thedistribution system; it allows any operable attachment point to be anenergy settlement and market-based financial settlement point, andprovides an interconnection to the attachment point. The model alsoindicates if devices are added, provides cost information for thedevices, lists the attributes of the devices, etc., which are used asinputs to generate a cost curve that determines how much the customerwill spend and funds receivable based upon participation in programs(e.g., encouraging sustainable or alternative energy).

The system includes a grid element catalog that includes attributes ofthe grid elements. Based upon customer inputs, the model indicatesoptions that match or fit the customer's profile. The model alsoprovides information about financing and energy capacity programs asprovided by REP, TDSP, independent system operator (ISO), RTO,community, FERC, and/or the governing body of the power grid. Once thecustomer selects a grid element, the system provides digital contractelements and/or financing terms associated with that grid element and/orcorresponding services. For example, installation, service, andmaintenance contract terms for generator, solar, etc. The digitalcontract is a standard form document between suppliers and consumers atwholesale or retail level. Digital contract terms are coordinatedthrough the platform for market participants (e.g., utilities,consumers, and all parties between the utility and consumer). Digitalcontract terms for a grid element device are presented as part of updatemessaging and/or programming, through a coordinator or distributeddatabase, or combinations thereof. Contract terms and data, includingbut not limited to financial settlements for grid elements and theirparticipation on or with any electric power grid, extend through thefields of the template and function as a complex rules engine to beadministered vis-à-vis the grid elements and related or correspondingservices, distributed architectures, networks, etc.

The GUI shows options for customers based on customer preferences, datagenerated by the customer, and the results of power modeling. End usecustomers (residential or commercial) are presented choices for gridelements, OEMs offering grid elements, energy plans, and service andmaintenance plans.

The platform makes calculations based upon the reliability of microgridsand/or DERs. These calculations are used to provide recommendations andupdated information to users in real time and/or near real time throughthe GUIs.

Electric vehicles or other mobile power storage devices on the microgridare part of the platform. The present invention allows for receiving,delivering, and/or discharging power from a mobile power storage device,interrupting the charging of that device, and combinations thereof witha portable market participant platform and corresponding GUI. Gridelements may decouple or couple to any pre-approved attachment point;this provides for dynamic interconnection of the grid element havingmobile power storage. The platform dynamically updates the model for thegrid upon confirmation of location or geo-detection of that gridelement. The platform also contains predictive analytics that showlocations in need of power inputs. Required components associated withthe mobile storage device or electric vehicle include at least a meterfor revenue grade metrology sufficient for market-based financialsettlement and at least one pre-approved attachment point for theinterconnect; the mobile storage device or electric vehicle must also beregistered with the platform. Pre-approved interconnection zones arethus provided for mobile grid elements; these zones and/or theiraggregation further provide for logical nodes for controlling orinputting power or load, demand response, etc. The zones may furtherfunction as balancing areas.

Utility Operator Interface

A utility operator interface provides a utility view for control roomstaff to control DERs with transparency. Maps, tables, and charts areapplied for illustration and view in regional or smaller areas. Regionalcontrol scenario algorithm and detail view control for specific premiseor units are applied for real-time behavior or run-mode adjustments tosupport grid operations.

FIG. 15 is a block diagram for the functions of a utility operatorinterface provided by an EnergyNet data platform. The utility operatorinterface provides utility operators with a utility view, map viewshowing DERs, aggregation bulk control in regional or smaller areas, anddetail view control for a specific premise or unit. In one embodiment,the map view of the utility operator interface includes a heat map ofDERs showing available capacity and running capacity. It provides atransparent view of utilization of assets in the field. In oneembodiment, a regional control scenario algorithm is used foraggregation bulk control. Current and/or historical weather and climatedata may be listed in a table. Detail view control provides real-timebehavior or run-mode adjustment to support grid operation.

FIGS. 16-22 are screenshots of a utility operator interface. FIG. 16shows a heat map of a distributed energy resource (DER) in a certainarea displaying production capacity distribution by circuit view. FIG.17 shows energy production in a certain area by region. Region name,production capacity, and production use are listed. A chart of availableproduction capacity vs. current use is also displayed. FIG. 18 shows aheat map of a DER in a certain region displaying production capacitydistribution by segment view. FIG. 19 shows a tabular and graphicaldescription of different segments. Segment status, segment name, zipcode, utility usage, the number of DERs sites in a segment, productionpotential, production use, and the microgrid configuration mode arelisted in a table. The microgrid configuration mode options include butare not limited to normal production and economic demand response. Whenthe utility cost is above a threshold, the microgrid in a certainsegment may be in economic demand response mode. Control room staff canperform segment control via the utility operator interface, for example,to change microgrid configurations. Production sources are presented ina pie chart listing the type of power source, including but not limitedto solar, generator, or storage. A bar graph of production vs.consumption is also shown, along with the average monthly production ofenergy per square foot, average monthly price per square foot for energyproduced, average monthly consumption of energy per square foot, andaverage monthly price per square foot for energy consumed. FIG. 20provides a map of different DERs sites in a certain segment andinformation regarding each site's configuration. Energy production,demand, and usage can be displayed for each site. The progress by siteis shown, including information about whether a site is online, in theplanning phase, or under interconnection review. A heat map includingthese different sites is also displayed. FIG. 21 provides a detailedenergy description of a specific site. A heat map showing the locationof the specific site is provided. Different energy sources, includingalternate solar, utility, and battery storage, are listed with theircurrent status, rate, and power usage. Solar energy production isillustrated in a bar graph, and values are shown for the currentproduction and average daily production. FIG. 22 describes the gridconfiguration of a specific site and shows the energy demand and usageof that site. Various configuration modes include normal operation,off-grid island, grid parallel, distributed generation, demand response,and black start support. Utility operators are enabled to activate acertain configuration mode. Demand and use is displayed graphically, andinformation about the real-time power usage, current energy usage,current daily cost, average energy usage, and average daily cost isprovided.

Interconnection Processing Interface

FIG. 23 is a block diagram for the functions of an interconnectionprocessing interface provided by an EnergyNet data platform. Theinterconnection processing interface enables a sales engineer for a DERprovider, demand response, curtailment response provider, or renewableenergy provider, or any assets deployed at transmission/distributionsystem level for electric power grids to facilitate interconnectionrequests and studies, system sizing and template, shopping and orderadjustments, and interaction with the utility interconnect desk. Theinterconnection processing interface also provides a validation functionwherein a sales engineer is unable to submit an incomplete system.

FIGS. 24-27 are screenshots of an interconnection processing interface.FIG. 24 shows interconnection progress by site. Address, productionconfiguration, average power, peak power, interconnection request stage,and time in progress are provided for each site. FIG. 25 displayspre-approved production packages. Descriptions of solar packagesincluding size, equipment needed (e.g., solar panels, backup batteries,and backup generators), average power, peak power, and the number ofimplemented packages are provided, as well as descriptions of generatorpackages including the average power, peak power, and number ofimplemented packages. The interface also includes a list ofinterconnects in progress and the time in progress. FIG. 26 displays thescope and technical description for an interconnection applicationsubmitted for review. The interface displays a description of the site,the package selected by the customer, the average power production, peakpower production, gateway, interconnect license information, utility,implementation zone, and installer. FIG. 27 displays information aboutthe interconnection agreement for an interconnection applicationassigned to an engineer for review. The interface displays the address,days in process, package selected by the customer, implementation zone,and installer; it also allows for design notes to be entered about theapplication.

Vendor/Aggregator View Interface

FIG. 28 is a block diagram for the functions of a vendor/aggregator viewinterface provided by an EnergyNet data platform. The interface enablesvendors/aggregators to browse distributed service provider customers,perform outreach, lower the cost of customer acquisition, and submitservices and devices for catalog content review.

FIGS. 29-31 are screenshots of a vendor/aggregator view interface.Vendors can see their portfolio and prospect for new sales via thevendor/aggregator view interface. FIG. 29 lists top customer segments,top sellers in the marketplace, top campaigns in the marketplace, andpre-approved production zones. FIG. 30 displays customer segmentresearch for vendors/aggregators. The platform is operable to allow avendor user from level 3 (L3) to search customers based on key words,for example, zip code. The system also presents vendors with GUIs orviews customers using relevant information such as address, meter status(e.g., active, inactive), meter type, client type (commercial orresidential), billing status, upgrades opt-in, building size, monthlycost, monthly energy consumption, cost per square foot, industry type,etc. FIG. 31 displays submission of a device for catalog content review.Vendors/aggregators can edit information regarding pricing, rebates, anddescriptions for a certain type of device, and provide informationregarding optional services offered.

Marketplace View Interface

FIG. 32 is a block diagram for the functions of a marketplace viewinterface. The marketplace view interface enables new customers todiscover what other customers are doing in the market, and enablesexisting customers to manage their portfolios on the market and seebundles and offers for transaction.

FIGS. 33-50 are screenshots of a marketplace view interface. Themarketplace view interface enables commercial, industrial, andresidential participants, such as homeowners or facility managers, tosee their energy information, shop for new products or services in themarketplace on the EnergyNet platform, and manage rate plans. FIG. 33 isa screenshot of the log in screen for a marketplace view interface.FIGS. 34-36 display various functions under the “Dashboard” tab in themarketplace view interface. FIG. 34 displays a customer's buildings on amap and information related to energy usage at the buildings. Theinterface provides a list of all buildings owned or managed by thecustomer, the monthly cost per square foot for each building, and allowsthe customer to compare buildings. FIG. 35 continues to illustrate themarketplace view interface of FIG. 34 with an overlay providinginformation about a specific building. The overlay lists the price persquare foot and energy rate for the building. FIG. 36 displays thedescription, energy rate, current/average usage, and daily cost for asite. The power sources for the site are listed (e.g., utility, solar,backup generator), and a summary of the account balance is shown.Additionally, a recommendation to configure the site's grid to connectto nearby microgrid producers is displayed.

FIGS. 37-42 display various functions under the “Energy Use” tab in themarketplace view interface. FIG. 37 displays current energy usage,including a real-time power usage chart, average daily power usage, peakdaily power usage, peak monthly power usage, cumulative daily energyuse, average daily energy usage, 30 day energy usage, and 30 dayreactive energy usage. FIG. 38 displays past energy usage, includingweekly use pattern, use by category, use trending, building usecomparison, and drift analysis. FIG. 39 is a screenshot of a marketplaceview interface allowing users to compare the energy use of differentbuildings. FIG. 40 continues to illustrate the marketplace viewinterface of FIG. 39 with an overlay showing a brief description of aselected building. FIG. 41 shows a usage and cost comparison between twobuildings. The interface also allows the user to compare the energy useof a specific building to the regional average. FIG. 42 continues toillustrate the marketplace view interface of FIG. 41 with an overlayshowing a recommendation to install an electric vehicle (EV) chargingstation.

FIG. 43 displays the current status of a customer's grid. Power sources(e.g., solar, utility, backup generator) are listed with real-timeand/or near-real-time status and power level, and real-time and/ornear-real-time UPS status and power levels are displayed. Graphicrepresentations of power usage efficiency (PUE) and carbon dioxideemissions are shown. A table showing source status, including the sourcename, status, and power level, is displayed. Additionally, arecommendation to configure the site's grid to connect to nearbymicrogrid producers is displayed, as well as a recommendation topurchase an upgraded battery storage device.

FIGS. 44-49 display various functions under the “Marketplace” tab in themarketplace view interface. FIG. 44 is a screenshot of the home page ofthe marketplace for commercial and industrial customers, residentialcustomers, and popular apps. The home page suggests completing abuilding survey for more recommendations. FIGS. 45 and 46 show upgradeoptions, including turnkey installation for EV charging stations,battery storage upgrades, and low interest financing on generatorupgrades. FIG. 47 shows a Rate Plan Selector as one of the servicesprovided by the marketplace. Recommended plans are listed based on theuser profile. Other plans are also listed and users may filter thelisted plans by information such as cost or plan type (e.g., all,renewable, fixed, variable). A user may select a plan by clicking the“Select Plan” button next to the plan. FIG. 48 continues to illustratethe marketplace view interface of FIG. 47 with an overlay showing adescription of the selected plan, including the simplified rate, planterms, and additional fees. If the user decides to select the plan, theycan do so by clicking “Enroll in Plan.” FIG. 49 displays other servicesprovided by the marketplace, for example, community solar installation,heating and air conditioning inspection and tune-up, and a leasingprogram for residential battery storage.

FIG. 50 displays the payment dashboard in the marketplace viewinterface. Payment status, marketplace recommendations, and a billingsummary are provided. The billing summary includes weekly history,energy usage, rate, change, and total for the rate plan. Users can alsoadd funds to the account through the payment dashboard.

Financial Settlement View Interface

FIG. 51 is a block diagram for the functions of a financial settlementview interface provided by an EnergyNet data platform. The financialsettlement view interface provides information regarding settlements,transactions, and revenue split payouts, as well as financial reports.The financial settlement view interface also enables utility back officestaff to see a view of revenue streams from the EnergyNet platform tothe utility. The supplied energy and consumed energy are also reconciledand provided in similar views such as a general ledger format. Ablockchain view may also be provided, wherein a list of nodes isprovided that show the number of transactions that are being publishedthrough the nodes, which allows users to view their node and status oftransactions through the node.

FIGS. 52-53 are screenshots of a financial settlement view interface.FIG. 52 displays the settlements dashboard of the financial settlementview interface. The financial settlement view interface is operable toshow different transaction types (e.g., energy production, gridelements, services, application programs) performed by the EnergyNetplatform and the percentage of financial settlements within theEnergyNet platform for each transaction type. The production transactiontype includes settlements between energy consumers and energy providers.The grid elements transaction type includes solar panels and backupgenerators. The services transaction type includes EnvironmentalProtection Agency (EPA) service, financing, installation, and ancillaryservices. An example of an ancillary service is regulationdown/regulation up in Electric Reliability Council of Texas (ERCOT). TheApps transaction type includes the building monitoring app and otherapps. The financial settlement view interface also displays marketplacecampaign information, including annual profit potential, and digitalcontracting status for different sites. A table of recent productionsettlements, including transaction number, energy rate, and settlementamount (value), is also shown. FIG. 53 displays recent transactionswithin the financial settlement view interface. Detailed information foreach transaction number is provided, including seller, buyer, rate,contract type, fuel mix, and value.

Tiers or Levels within the EnergyNet Platform

One embodiment of the present invention is a system of an advancedenergy network, comprising a platform communicatively connected to atleast one distributed computing device operable for providing inputsfrom at least one energy user, wherein the platform is operable to:create a user profile for the at least one energy user; collect energyusage data for the at least one energy user; associate the energy usagedata with the user profile corresponding to the at least one energyuser; aggregate the energy usage data; estimate projected energy usagefor the at least one energy user; predict energy consumption data basedon the energy usage data and the projected energy usage data; and storethe energy usage data, the projected energy usage data, and thepredicted energy consumption data in a database. In Level 0 (L0) of thepresent invention, the user or consumer is engaged in the platform byproviding verified information on actual energy usage to the platform.In Level 1 (L1) of the present invention, the user may provideadditional information to the system and/or additional information maybe gathered from public sources. In Level 2 (L2) of the presentinvention, the user may add grid elements to their user profile. InLevel 3 (L3) of present invention, the utility, grid element vendors,meter data aggregators, etc. may identify sales opportunities based ondata in the database and provide marketing for products and/or serviceofferings to consumers (consumer users) or commercial users withprofiles within the EnergyNet platform. In Level 4 (L4) of the presentinvention grid elements operable for providing electric power supply (byway of example and not limitation, solar power generation, fuel cell orbattery power storage devices, wind generation, back-up powergenerators, etc.) that are properly constructed and configured, modeled,and connected with revenue grade metrology acceptable for energysettlement and market-based financial settlement within the energymarket, are introduced after being registered and profile created withinthe EnergyNet platform.

In one embodiment, for level 0 (L0) the actual energy usage datadocumented within a utility bill is uploaded to the platform by anenergy user having a profile or creating a profile on the EnergyNetplatform. The actual energy usage data is uploaded and communicated overat least one network to at least one computer or server associated withthe platform, which automatically recognizes the format of the utilitybill based upon prior utility bill(s) uploaded by at least one user. Forexample, if a first user uploads a utility bill to the platform andselects the relevant information from the utility bill, the platform mayautomatically recognize the format of utility bills for subsequent userswho have the same service provider. Also or alternatively, the energyuser inputs indication of which data to capture from the utility billfor automatic association with that user's profile. The system alsoprovides options for the energy user to selectively redact informationon the utility bill, such as customer name, account number, and PINnumber. The platform may automatically populate the database based onthe data on actual energy usage in the utility bill. The platform isfurther operable to collect at least one of real-time or near real-timedata from grid elements and data from smart meters associated with theat least one user.

FIG. 54A and FIG. 54B are screenshots of a utility bill verification foran electric bill. The utility bill is shown on the left side of thescreen in FIG. 54A. The system extracts the relevant information fromthe utility bill, such as service address, bill date, and currentcharges for electricity from the bill as shown in FIG. 54B. The systemallows users to select the relevant information to be extracted. In apreferred embodiment, the user can adjust the selection overlays withmatching colors on the bill by dragging the overlays or their corners asneeded. If the information is still incorrect after adjusting theselection overlays, the user can modify the values in the fieldsthemselves. When all fields are correct, the user can verify the valuesin the fields by pressing the confirm button as shown in FIG. 54B. Ifthe system recognizes the format of the utility bill, it automaticallypopulates the fields in FIG. 54B with the name of the electric provider,service address, building type, bill date, and current charges.Information such as the customer name, account number, and PIN numbermay be redacted by the system and/or user inputs as shown in FIG. 54A.FIG. 55A and FIG. 55B are screenshots of a utility bill verification foran electric and gas bill. The utility bill is shown in FIG. 55A. Thesystem populates the current charges field in FIG. 55B with the electriccharges and does not include “Other Charges & Credits” in the valuepopulated in the field.

The embodiments disclosed make use of the “user profiles” concept. Theuser profile includes, but is not limited to, the following: (1) energyuser name; (2) service address; (3) electric provider; (4) buildingtype; (5) historical and current bill dates; and (6) historical andcurrent charges for electrical service. The user profile may furtherinclude information regarding geodetic location; meter ID; customerprograms (possibly including program history); device information,including device type and manufacturer/brand; user energy consumptionpatterns; and connection and disconnection profile. Theconnection/disconnection profile can include service priority (i.e.,elderly, police, etc.) and disconnection instructions.

In other embodiments, additional data called “variability factors” maybe captured by the system as part of the user profile, including, butnot limited to, the following: (1) outside temperature, (2) sunlight,(3) humidity, (4) wind speed and direction, (5) elevation above sealevel, (6) orientation of the service point structure, (7) duty durationand percentage, (8) set point difference, (9) current and historic roomtemperature, (10) size of structure, (11) number of floors, (12) type ofconstruction (brick, wood, siding etc.) (13) color of structure, (14)type of roofing material and color, (15) construction surface ofstructure (built on turf, clay, cement, asphalt etc.), (16) land use(urban, suburban, rural), (17) latitude/longitude, (18) relativeposition to jet stream, (19) quality of power to devices, (20) number ofpeople living in and/or using structure, (21) age of structure, (22)type of heating, (23) lot description, (24) type of water, (25) othersquare footage, and (26) other environmental factors. Additional datathat may be stored by the system include vacancy times, sleep times, andtimes in which control events are permitted. User profiles may alsoinclude whether a swimming pool is located at the service address.

In level 1 (L1) of the present invention, the user may provideadditional information to the system and/or additional information maybe gathered from public sources to further populate the user profile.Information regarding the plurality of variability factors may obtainedfrom public sources. For example, information regarding weather (e.g.,outside temperature, sunlight, humidity, wind speed and direction) maybe obtained from publicly available weather services. Additionally,information regarding size of structure (e.g., square footage), numberof floors or stories, type of roofing material, type of construction,age of structure, type of heat, etc. may be found on publicly availablewebsites (e.g., county or state records, Zillow, and Trulia). Users maybe given incentives to provide additional information for their userprofile.

The user profile may further contain information regarding userpreferences, wherein the user preferences comprise at least one ofautomatic uploading of utility bills, contact preferences, paymentpreferences, privacy preferences, renewability of energy sources, gridelement preferences, rate plans, consumption, cost, locality, and marketsupply.

The platform uses information in the user profile to generate moreaccurate predictive consumption data. For example, if one energy useruploads a utility bill, that utility bill may be used to generatepredictive consumption data for similar structures or similar geographiclocations (e.g., houses in the same neighborhood). If additional energyusers upload utility bills, the aggregated data from the utility billsmay be used to generate more accurate predictive consumption data. Withadditional information, such as variability factors, the platform isable to increase the accuracy of the prediction. For example, a housewith a pool and an electric vehicle would be expected to use moreelectricity than a house in the same neighborhood without a pool orelectric vehicle. Additionally, a larger house or multi-story housewould have a larger predictive energy consumption than a smaller houseor single-story house in the same neighborhood. Also, typically olderhouses have lower energy efficiency, due to factors affecting energyconsumption, e.g., older HVAC equipment that is less efficient thanmodern equipment, and/or factors affecting the leakage of conditionedair, e.g., less insulation, older windows and doors, etc. Variabilityfactors may be added to the system by users or obtained from publicsources of data.

The platform is further operable to display a map of the predictedenergy consumption as shown in FIGS. 56-59. FIG. 56 shows an electricityspend map zoomed out to show the Continental United States. FIG. 57shows an electricity spend map zoomed in to the region level. The area,electrical spend summation, electrical spend count, electrical spendaverage, electrical spend minimum, and electrical spend maximum arelisted in a table. FIG. 58 shows an electricity spend map zoomed in tothe district level. The state, area, electrical spend summation,electrical spend count, electrical spend average, electrical spendminimum, and electrical spend maximum are listed in a table. FIG. 59shows an electricity spend map zoomed in to the neighborhood level. Thezoomed in map is a satellite image showing houses in a particularneighborhood. The electrical spend summation, electrical spend count,electrical spend average, electrical spend minimum, and electrical spendmaximum are listed in a table. The electrical spend for each house isshown above the house.

In Level 2 (L2) of the present invention, the system receives userinputs that associate at least one grid element with their correspondinguser profile. The grid elements include but are not limited to powertransfer switches, wind meters, utility meters, battery dischargecontrollers, tenant sub-meters, solar meters, power distribution units(PDUs), appliance switches, electric vehicle charging stations,distributed energy resources (DERs), transfer switches, electric vehiclebatteries, inverters, controllable loads, weather stations, and/or HVACenvironments. For example, the system may receive an indication orselection inputs from a user regarding a present or future interest in,or action for installing and operating of, solar panels to their rooffor the location associated with their corresponding user profile; thischange and the user's preferences or profile regarding the solar panelsis saved in the database.

In Level 3 (L3) of present invention, the at least one utility or marketparticipant and its partners (e.g., vendors) utilize the EnergyNetplatform to identify sales opportunities based on data in the database.Data that is anonymized or permission-based access to data from userprofiles may be used to provide insights on inefficient devices,defective devices, or devices that require updating to meet currentstandards. User profile data may also be used to identify related salesopportunities. For example, if energy consumption patterns suggest thatthe user may be very interested in personal energy conservation, thensales efforts could be directed toward that individual concerningproducts related to that lifestyle. This information can be used by theutility or its partners to provide incentives to users to buy newer,updated devices, or obtain maintenance for existing devices. The user isgiven the option to opt out of having his user profile used for salesand marketing efforts, or for regulating energy conservation. The userprofile makes use of open standards (such as the CPExchange standard)that specify a privacy model with the user profile. The use ofconsumption patterns in this manner is governed by national, state, orlocal privacy laws and regulations.

A further embodiment of using user profiles to identify salesopportunities involves the use of device information to createincentives for users to replace inefficient devices. By identifying theknown characteristics and/or behavior of devices within a service point,the invention identifies those users who may benefit from replacement ofthose devices. The invention estimates a payback period for replacement.This information is used by the utility or its partners to createredemptions, discounts, and campaigns to persuade users to replace theirdevices.

Users may be grouped by geography or some other common characteristics.For example, groups might include “light consumers” (because theyconsume little energy), “daytime consumers” (because they work atnight), “swimmers” (for those who have a pool and use it), or othercategories. Categorizing users into groups allows the utility or itspartners or market participants to target sales and marketing efforts torelevant users.

EnergyNet Graphs

FIG. 60 is a screenshot of a sample settlement pricing zone. The blueshaded areas with dark outlines in the figure are settlement zonescorresponding to traditional settlement zones established by energymarkets, e.g., ERCOT, wherein the market (ERCOT) determines thegeographic zones that comprise the settlement zones, wherein electricpower grid resources settle energy supplied and load consumed to thenearest resource point or settlement point, which are shown in theadditional map layers in FIG. 61. Anything northwest of the blue shadedzone with dark outlines illustrated settles in the uppermost settlementarea marked with a “$” on the map. Larger grid elements, by way ofexample and not limitation, power plants, substations, transmissioninterconnections, large commercial or industrial locations with theirown substations, are also identified and energy settlement andcorresponding market-based financial settlement by the market (e.g.,ERCOT), which also defines them within its settlement zones and definesthe pricing node for them. Locational marginal price (LMP) is based uponwhere the grid elements (supply or load grid elements) are relative tothe blue settlement area with dark outlines marked with a “$” on themap.

FIG. 62 is a screenshot showing a satellite image of actual settlementpoints. The interface allows the user to zoom in with satellitephotography to identify each grid element, e.g., power plant,substation, large commercial and/or industrial grid elements or powersupply grid elements. The zones are close together in this view becausea commercial facility is drawing significant amounts of power off thedistribution of electrical power of the grid. Also illustrated are apower plant and light commercial and/or industrial, and residentialconsumers in that second zone. While these grid elements and electricpower loads exist and are identifiable within the GUIs and within theEnergyNet platform and system, within the EnergyNet platform thetraditional zones and nodes established by the market (e.g., ERCOT) aresubdivisible into logical points below the LMP or settlement nodes. Thesystems and methods of the present invention are operable to aggregateand/or directly control load below these traditional zones, nodes, andattachment points. While new loads and new power supply (e.g., newgeneration source) may be introduced and operable below the traditionalzones or nodes, the market (e.g., ERCOT) will not have data associatedwith those newly introduced and operable grid elements (for load and forsupply) unless it is supplied to the market via the EnergyNet platform.For example, if a solar generation grid element and solar energy fuelcell or storage is introduced to the electrical power grid via theEnergyNet platform and located within one of the illustrated traditionalzones, then it is operable to start introducing power for distributionat the proximal substation. The market would only be able to detect thata lower amount of electrical power is being drawn at the substationlevel or traditional zone. However, after the solar generation gridelement and solar energy fuel cell or storage is registered and activewithin the EnergyNet platform, energy settlement and market-basedfinancial settlement for the electrical power introduced or supplied tothe electric power grid is provided at the point of attachment(attachment point) for those solar grid elements. This contrasts withprior art, where the market cannot detect or settle energy or providefor market-based financial settlement below the traditional zones orsubstation level.

FIG. 63 is a screenshot of an overview of ERCOT Settlement Zones. Thenumber inside the point represents the number of nodes geographically ateach point. For example, there are 17 subnodes within the locationmarked with a “17” on the map, and 16 subnodes within the locationmarked with a “16” on the map; these subnodes correspond to ERCOTsubnodes, which provide for settlement zones at Level 4 within thesystem.

Financial Model Visualization Interface

A financial model visualization interface allows at least one utility ormarket participant, to run Monte Carlo simulations for adding new metersto the market, energy usage distribution, and/or energy generationdistribution. Adjusting the simulation parameters (e.g., mean, standarddeviation, skewness) provides for minimizing or managing risk fordecision-making and investment related to the electric power grid, andto better predict outcomes.

FIG. 64 is a screenshot of the log in screen for a financial modelvisualization interface. In a preferred embodiment, the user can sign into system and authorize the application with an account provided by athird party, e.g., Google. FIG. 65 is a screenshot showing the selectionof the financial model from the dropdown menu. FIG. 66 is a screenshotof a financial model page. The left half of the screen shows a meterinstallation population density attraction with a heat map. Theattraction percentage can be adjusted with a sliding bar. The right halfof the screen shows the rate of new meters added to the market. The meanrate of new meters added to the market per day, the standard deviation,and the skewness can be adjusted with a sliding bar. A graph displaysthe rate of new meters added to the market based on the mean, standarddeviation, and skewness selected. FIG. 67 is a screenshot showing kWhUsage Distribution and kWh Generation Distribution. These left half ofthe screen shows kWh Usage Distribution. The mean energy usage, standarddeviation, and the skewness can be adjusted with a sliding bar. A graphdisplays the kWh usage distribution based on the mean, standarddeviation, and skewness selected. The right half of the screen is todisplay kWh Generation Distribution. Users would be able to adjust themean energy generation, standard deviation, and the skewness in much thesame way as for kWh Usage Distribution. A graph could also be displayedwith the kWh generation distribution based on the mean, standarddeviation, and skewness selected. Skewness values may differ forresidential, commercial, and industrial uses.

FIG. 68 is a screenshot of a simulation showing meter distributionsrandomly added to the map over time. A map is shown on the left half ofthe screen showing a meter heatmap with the dots representing meters. Agraph is shown on the right half of the screen showing the increase inthe number of meters on the y-axis and time on the x-axis based on theparameters selected. FIG. 69 continues to illustrate the screenshot ofFIG. 68 with additional map layers for ERCOT Settlement Points. The usercan select the following levels: meters, meter heatmap, settlementpoints, settlement regions, and usage heatmap. The user can also viewthe map as open street, grayscale, and streets. A map is shown on theleft half of the screen showing a meter heatmap, settlement points,meters, and settlement regions. A graph is shown on the right half ofthe screen showing the increase in the number of meters on the y-axisand time on the x-axis based on the parameters selected.

The following are incorporated herein by reference in their entirety:the NY REV order, CAL ISO rules and proposed rules and subsequent orderfor DER marketplace, ERCOT presentation stakeholder concerns, and termsand their definitions: telemetry light, telemetry medium, etc.

Certain modifications and improvements will occur to those skilled inthe art upon a reading of the foregoing description. For example,Software as a Service (SaaS) or Platform as a Service (PaaS) may beprovided in embodiments of the present invention. Also, updatedcommunications such as 5G and later alternatives are considered withinthe scope of the present invention. The above-mentioned examples areprovided to serve the purpose of clarifying the aspects of the inventionand it will be apparent to one skilled in the art that they do not serveto limit the scope of the invention. All modifications and improvementshave been deleted herein for the sake of conciseness and readability butare properly within the scope of the present invention.

What is claimed is:
 1. A system for managing an advanced energy networkcomprising: a server platform constructed and configured fornetwork-based communication with an electric power grid and at least onecomputing device; wherein the electric power grid includes amultiplicity of grid elements; wherein the server platform is operableto provide at least one interactive graphical user interface (GUI) forthe at least one computing device; wherein the server platform isoperable to: create a device profile for at least one device via the atleast one interactive GUI; collect energy usage data from themultiplicity of grid elements; build a power model of the electric powergrid via the at least one interactive GUI based on the energy usage datafrom the multiplicity of grid elements, historical data of themultiplicity of grid elements, and/or a current environment of theelectric power grid; control a participation of at least one of themultiplicity of grid elements based on market information and revenuegrade metrology data for the at least one of the multiplicity of gridelements in real-time or near real-time; perform energy financialsettlements for the participation of the at least one of themultiplicity of grid elements based on the market information and therevenue grade metrology data; and generate and transmit predictiveenergy consumption data, control information for the participation ofthe at least one of the multiplicity of grid elements, and energysettlement data to the at least one computing device for displaying thepredictive energy consumption data, the control information for theparticipation of the at least one of the multiplicity of grid elements,and the energy settlement data via the at least one interactive GUI. 2.The system of claim 1, wherein the predictive energy consumption data isbased on the energy usage data and the historical data of themultiplicity of grid elements.
 3. The system of claim 1, wherein theserver platform is operable to collect historical energy usage data froma utility bill uploaded to the server platform, and wherein the serverplatform is further operable to automatically recognize the format ofthe utility bill.
 4. The system of claim 1, wherein the server platformautomatically populates a database based on historical energy usagedata, and wherein the database stores the energy usage data and thepredictive energy consumption data.
 5. The system of claim 1, whereinthe predictive energy consumption data is based on a plurality ofvariability factors including outside temperature, sunlight, humidity,wind speed and direction, elevation above sea level, orientation of aservice point structure, duty duration and percentage, set pointdifference, current and historical room temperature, size of structure,number of floors, types of construction, color of structure, type ofroofing material and color, construction surface of structure, land use,latitude and longitude, relative position to jet steam, quality of powerto device, number of people living in and/or using structure, age ofstructure, type of heating, lot description, type of water, squarefootage, and/or other environmental factors.
 6. The system of claim 1,wherein the server platform is further operable to display a mapincluding the predictive energy consumption data.
 7. The system of claim1, wherein the participation of the at least one of the multiplicity ofgrid elements includes supplying, consuming, and/or curtailing power. 8.A system for managing an advanced energy network comprising: a serverplatform constructed and configured for network-based communication withan electric power grid and at least one computing device; wherein theelectric power grid includes a multiplicity of grid elements; whereinthe server platform is operable to provide at least one interactivegraphical user interface (GUI) for the at least one computing device;wherein the server platform is operable to: build a power model of theelectric power grid via the at least one interactive GUI based on energyusage data from the multiplicity of grid elements, historical data ofthe multiplicity of grid elements, and a current environment of theelectric power gird; control a participation of at least one of themultiplicity of grid elements based on market information and revenuegrade metrology data for the at least one of the multiplicity of gridelements in real-time or near real-time; perform energy financialsettlements for the participation of the at least one of themultiplicity of grid elements based on the market information and therevenue grade metrology data for the at least one of the multiplicity ofgrid elements in real-time or near real-time; and transmit predictiveenergy consumption data, control information for the participation ofthe at least one of the multiplicity of grid elements, and energysettlement data to the at least one computing device.
 9. The system ofclaim 8, wherein the server platform is further operable to build a proforma power model, and wherein the pro forma power model includes atleast one generator and/or at least one load device.
 10. The system ofclaim 8, wherein the server platform is operable to dynamically updatethe power model of the electric power grid when a grid element iscoupled to or decoupled from the electric power grid.
 11. The system ofclaim 8, wherein the server platform is operable to create a deviceprofile for at least one device via the at least one interactive GUI,wherein the device profile includes energy consumption data, an energyrate plan, at least one grid element associated with the at least onedevice, a service address, a building type, historical and/or currentbill dates, a geodetic location, and/or a customer program enrollmentstatus.
 12. The system of claim 8, wherein the power model is operableto recommend a power usage plan based on a set of energy preferencesincluding a cost, a payment preference, renewability of energy, marketsupply, energy consumption data, and/or minimum and maximum usageconstraints.
 13. The system of claim 8, wherein the power model isoperable to provide an interconnection for a point of attachment for theat least one of the multiplicity of grid elements and at least onemarket-based financial settlement point.
 14. The system of claim 8,wherein the power model is operable to provide energy financinginformation and/or energy capacity program information via the at leastone interactive GUI.
 15. The system of claim 8, wherein the serverplatform is further operable to generate a cost curve based on the powermodel, wherein the cost curve indicates a predicted energy consumptioncost and/or a funds receivable value based upon participation in atleast one energy program.
 16. A system for managing an advanced energynetwork comprising: a server platform constructed and configured fornetwork-based communication with an electric power grid and at least onecomputing device; wherein the electric power grid includes amultiplicity of grid elements; wherein the server platform is operableto provide at least one interactive graphical user interface (GUI) forthe at least one computing device; wherein the server platform isoperable to: create a device profile for at least one device; build apower model for the electric power grid based on energy usage data fromthe multiplicity of grid elements, historical data of the multiplicityof grid elements, and/or a current environment of the electric powergrid; generate predictive energy consumption data; control aparticipation of at least one of the multiplicity of grid elements;perform energy financial settlements for the participation of the atleast one of the multiplicity of grid elements; and transmit thepredictive energy consumption data, control information for theparticipation of the at least one of the multiplicity of grid elements,and energy settlement data to the at least one computing device fordisplaying the predictive energy consumption data, the controlinformation for the participation of the at least one of themultiplicity of grid elements, and the energy settlement data via the atleast one interactive GUI.
 17. The system of claim 16, wherein theserver platform is operable to perform settlements for electrical powerintroduced and/or supplied to the electric power grid at a point ofattachment for the at least one of the multiplicity of grid elements.18. The system of claim 16, wherein the at least one interactive GUIincludes at least one view interface operable for searching energycustomers, managing energy portfolios on a marketplace, displayinginformation for energy transactions, controlling and displayingbehaviors of distributed energy resources (DERs) in the electric powergrid, displaying a heat map of DERs including available and runningcapacity, facilitating interconnection requests and studies in theelectric power grid, visualizing meter installation, visualizing energyusage distribution, and/or visualizing energy generation distribution.19. The system of claim 16, wherein the server platform is operable toprovide information contained in the device profile for sales andmarketing efforts by at least one of a vendor, a utility, and/or autility partner, and wherein the information contained in the deviceprofile is anonymized.
 20. The system of claim 16, wherein the energysettlement data is aggregated into at least one settlement block inreal-time or near real-time, and wherein the at least one settlementblock includes revenue grade metrology data for the at least one of themultiplicity of grid elements.